Recovering Object identifiers

I created two new objects in DOORS and then didn't save when unlocking. Is there a way to recover them?  The object identifiers created are in use in other documents (not in DOORS) and it would be much easier if I can recover or modify the Object IDs to march these. Is this possible?

 

 


U6X7_paul_kostek - Thu May 21 13:54:31 EDT 2015

Re: Recovering Object identifiers
kourosh - Fri May 22 15:24:06 EDT 2015

If you didn't save then no, they can't be recovered. And the absolute number is also not modifiable. The absolute number is intended to be a unique identifier. If you want a separate requirements ID that you can control, that will need to be a user-defined attribute.

Re: Recovering Object identifiers
U6X7_paul_kostek - Fri May 22 15:57:34 EDT 2015

kourosh - Fri May 22 15:24:06 EDT 2015

If you didn't save then no, they can't be recovered. And the absolute number is also not modifiable. The absolute number is intended to be a unique identifier. If you want a separate requirements ID that you can control, that will need to be a user-defined attribute.

Thanks - that is what I figured, but thought I'd ask,

Re: Recovering Object identifiers
llandale - Thu May 28 16:42:07 EDT 2015

kourosh - Fri May 22 15:24:06 EDT 2015

If you didn't save then no, they can't be recovered. And the absolute number is also not modifiable. The absolute number is intended to be a unique identifier. If you want a separate requirements ID that you can control, that will need to be a user-defined attribute.

I have fiercely argued for "Requirement ID" attribute to reference the object, forgoing the "Object Identifier" favored by most folks.  I have had little success arguing my minority opinion.   ReqIDs are difficult to implement; as keeping track of such a list of IDs is very cumbersome.

But then I had a revelation, we can have our cake and eat it too.  the "Requirement ID" of an object is its "Object Identifier" unless specifically stated otherwise.  So we add two attributes to the requirement modules:

  • "ReqID Override"; string; usually empty but otherwise contains the Req ID of the object
  • "ReqID"; string; attr-DXL: has the value of the Override if non-null, otherwise has the value of the Object Identifier.

ReqIDs look like ObjIDs.  Everybody references the ReqID attribute.

Now in the Original poster's case, when a reference has been lost but is still in use, we would do the following:

  • So far, ReqID Override is empty for all objects
  • create two new objects.  Assign ReqID Override to the Object ID of the two missing objects.

Viola.

  • You need a mechanism of preventing the ObjID of the two new objects (with Overrides) from being used by other Overrides.
  • It would behoove you to purge Objects whose ID is used as an Override.
  • You need to make sure your Module Prefixes are meaningful and unique within the project.  Thus your Object IDs and therefore your Requirement IDs can be used to uniquely find the referenced object.

-Louie